Conversation
We had two changes in composefs-rs: - xattr filtering - v1 vs v2 EROFS When we switched to v1 for the EROFS generation by default, it broke UKI upgrades when the system was deployed with an older bootc. Unfortunately, there's no easy way to fix this (short of reverting the change to v1 by default). But at least with this approach, one can more easily temporarily use a newer bootc on the client, and it will be able to adapt to e.g. having an *older* bootc (perhaps using v2) in the target environment. Assisted-by: AI Signed-off-by: Colin Walters <walters@verbum.org>
cgwalters
force-pushed
the
composefs-xattr-fallback
branch
from
August 31, 2026 16:33
f3e5410 to
2c13a60
Compare
Collaborator
Author
|
Merging with #2248 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We had two changes in composefs-rs:
When we switched to v1 for the EROFS generation by default, it
broke UKI upgrades when the system was deployed with an older
bootc.
Unfortunately, there's no easy way to fix this (short of
reverting the change to v1 by default).
But at least with this approach, one can more easily temporarily
use a newer bootc on the client, and it will be able to adapt
to e.g. having an older bootc (perhaps using v2) in the target
environment.
Assisted-by: AI
Signed-off-by: Colin Walters walters@verbum.org